Subject: Conference Call On Wednesday

From: "Shannon Nix" <[email-masked]>
Date: Mon, 10 Apr 95 14:43:41

Howdy mibbers,
     
     The working group met last week in Danvers for three sessions.  The 
     latter two were consumed in a detailed review of the MIB draft.  This 
     did not complete however, and so, in order to preserve the momentum, 
     the majority of those present chose to reconvene on Wednesday of this 
     week (Apr 12) in Raleigh and to conference any other interested 
     parties in to this session.  The goal is to complete the review so 
     that we may produce another draft of the MIB prior to AIW, the first 
     week in May.
     
     I have attached some rough minutes of the Danvers review (these will
     be polished up and included in the proceedings).  We made it part-way 
     through the TConnTable (I think we were up to about pg 42)
     
     Cisco have volunteered a conference room with speaker phone for those
     in Raleigh.  We will meet there at about 9:00 on Wednesday morning.
     
     Directions - 
       1. Take the belway to US 1 North
       2. Highwoods Dr to the left (first light after the exit???)
       3. Left on Smoke Tree Court
       4. 11 story glass faced building.
       5. Reception on 10th floor.
       6. Ask for Ravi 
     
     For those interested in participating by phone, mail me a response
     tomorrow, leaving me a number where you can be reached on Wednesday
     morning.  I will make arrangements, based on number of interested 
     parties.
     
     The latest draft can be FTPed from
     
     networking.raleigh.ibm.com
     
     /aiw/dlsw/mib/*3.txt
     
     Best Regards,
     Shannon
     
     Minutes follow:

1.  Set agenda

    Session 1   Tue   9:00-11:30
    Session 2   Wed   9:00-11:30
    Session 3   Wed  19:30-22:00

    Tutorial    30 minutes
    Issues      30-60 minutes
    Conformance 15-30
    Traps       15-30
    Walkthru    Remainder
    
2.  DLSW Overview - Peter (get slides for proceedings)

3.  MIB Overview - Dave ( get slides for proceedings

The group then began to review some previously posted lists of issues.  It 
became apparent that most of those issues could be more methodically addressed
in a detailed walkthrough.  So the remainder of the exercise was deferred
to the walkthrough.  I have consolidated the resolution of the issues
into the summary of the walkthrough results.

4.  Issues

    Peter Gayek
    
    1a. Need DLSw TCP domain which denotes Taddr format of the above. 

    2.  Pg 28 delete ...ReadPortNumber ? always 2065
        
    3.  Pg 54 remove dlswTConnTcpOperConnTable. Could add back
        in future for >2 transport connections.
        
    4.  Pg 33 dlswTConnTable add object reflect ...VirtualChannels
    
    5.  Pg 28 ..TcpSession  -> dlswTransportVirtualChannels
    
         "The number..." -> "The preferred number"
         
         Add DEFVAL of 2
         
         Bound range to 31
         
    6.  Pg 30-32 DefOpen/Close... and ...DynOpen/Close...
    
        condense to 3 objects (remove Def/Dyn)???

         Change name (AND MOVE) to geniricize ("VirtualChannel")

    7.  Things that have ROW-STATUS need to be read-create.     
    
    8.  Collapsing Cache and Capex entries?

Prior to the detailed walkthrough, however, some discussion occurred 
regarding conformance groups.  The following groups were proposed:
    
    1. Base conformance group( forward SNA (LAN) over a generic transport)
    2. TCP as a tranport
    3. NetBIOS  
    4. DirectorySearchCapability
    5. SDLC as a data link
    6. CacheTableSupported
       
It was further, agreed, that compliance statements should be drafted
to relax the MIN-ACCESS of all read-write objects to read-only       

David Chen shall draft a straw-man applying the existing objects to these
groups:

Sessions two and three (and lunch and dinner :-) were occupied with
the detailed walkthrough.  The results of this are appended to this
document.

Prior to adjourning, the group developed the following action plan:

  1. Minutes shall be posted this week (by April 7).
  2. Conference call shall be scheduled on Wed., April 12, at 12:00 EDT to
     complete the walkthrough.  This will begin following the dlswTConnTable
     objects. (Details to follow)
  3. David Chen shall update the draft to reflect the results of the
     complete walkthrough and post prior AIW
     
  4. The group will convene at AIW in San Jose, the first week of May to
     review the new draft.
     
DETAILED WALKTHROUGH:    
     
The remainder of this document outlines the results of the detailed walk-
through on a page-by-page basis.         

*******  SESSION 2

0.  Pg 5
     Update text on conformance groups to reflect the above

0a. Pg 13 TADDR should have only IP address (no port numbers)
          If there are multiple port pairs between two peers,
          then they shall be considered as one transport.
               
1.  Pg 15

    Remove ...XBusySupport
    
    ..PacingSupport renamed ..StandardPacingSupport
    
    ..*VirtualSegment
       needs more granularity Two proposals
          move to LAN interface
          move to Transport -- Action S. Nix
          
    ..*VirtualSegmentSize
    
       depends on      
       
    Admin/Oper paradigm questioned...
    
        Collapse *VirtualSegmentLFSize into one object
        Collapse *Status and Move toward front of this section
          and change enum to
             enable,
             disable

Pg 17
        
    ..UpTime need text ( subagent - sysUpTime equivalent or tied to Status)
        Timeticks???

Pg 18
    
    Range on RecWndwSize (0..63) 
    
Pg 19

    ..*ForwardingStatus (NB and SNA)
    
    Move ..OutOfResourceTraps closer to TRAP definitions
    
Pg 20
    
    Rename ..AdminSnaSapList -> ..AdminSapList

    Collapse ..*SapList (Admin & Oper)
    
    ResourceApplyTimer removed - replaced with text describing
      implementation option and example
      
      remove all refs to ApplyTimer in DESC clauses
      
    Remove ResourceSnaSend
    Remove ResourceSnaReceive
      (Could change filter on the other side)
      
Pg 21

    Remove ResourceNBSend
    Remove ResourceNBReceive       
    
Pg 22
    Collapse ..*ResourceNBExclusivity (Admin/Oper)
      remove other from enum..leaving
        nonExclusive
        exclusive
      remove reference to ApplyTimer
      
Pg 23
    Remove ..NBApplied
    
    Add ...ResourceNBNameType
      enum
        group,
        individual               
        
Pg 24

    Remove ..MacSend
    Remove ..MacReceive  (same rationality)

    Collapse *MacExclusivity (admin/oper)
      remove other from enum..leaving
        nonExclusive
        exclusive
    
Pg 26
    Remove ..MacApplied object
    
Pg 27
    dlswTransportTable was replaced by the following proposed table
    which allows local administration for all transport connections in a
    DLSw node:
    
    The proposed dlswTGroupTable:

     dlswTGroupIndex (arbitrary integer index)
     dlswTGroupTDomain ( transport domain for this row)
     dlswTGroupLocalTAddr ( local transport address for this row)
     dlswTGroupRemoteTAddr ( remote transport address for this row)
     dlswTGroupRemoteTAddrMask ( Mask to apply to remote transport address
     dlswTGroupSetupType  (enumerated)
        other,      ( Reserved for vendor specific)
        idle,       ( Don't use this row to establish circuits)
        passive,    ( Listen for connections from remote addr/mask)
        active,     ( Attempt to establish transport connection with remote
                      partner (mask must be all ones))
        (this enum can be grown in the future..ie. on-demand)              
        
     dlswTGroupDesiredCircuits  (desired number of full duplex transport 
                                 connections to established with partners
                                 matching this row.  Zero (the default) 
                                 means two simplex transports)
     dlswTGroupSegmentSize      (for TCP this would be the TSS)
     dlswTGroupKeepAliveInt     (interval to send keep-alives)
     dlswTGroupInitPacingWindow
     dlswTGroupRowStatus        ( Row creation mechanism)                            

     NOTE: There is some support to also maintain rows with a common
           index for transport-specific objects.  Of the above objects
           (for TCP) the following objects would probably be included
           in such a table.
           
           dlswTGroupTCPTable (indexed by dlswTGroupIndex)
           
           ...RemoteTAddr      -> ...RemoteIPAddr
           ...RemoteTAddrMask  -> ...RemoteIPAddrMask      
           ...SegmentSize      -> ...SegmentSize
           ...KeepAliveInt     -> ...KeepAliveInt
           
           However, there was no clear concensus on this issue.
           
           Another proposed variation of the above transport-specific
           table was to have the T/S table independently indexed and the
           index into the T/S table included in the dlswTGroupTable.

Pg 28
     Remove all TCP-Specific Node Objects.  Note that most of these 
     were moved into the above table (dlswTGroupTable)
     
Pg 29
     Move dlswEnable*Trap objects nearer to the traps.
     
Pg 30
     Change TConnEntries -> TConnActiveEntries (derives)

Pg 30-32 DefOpen/Close... and ...DynOpen/Close...
        Remove *Open
        condense to 2  objects (remove Def/Dyn)
        CloseIdle,
        CloseBusy
        
        Definition of normal is closed with no active circuits!
        
Pg 35
     Remove RowStatus
     
     Add object reflect ...VirtualChannels (read-only)
     Add object to point back to TGroup Row (zeroed if changed)
     
Pg 36
     ConnUpTime is a snapshot of EntryUpTime (not delta from present)     
     State add enum val:
             disconnected
             connecting
             init-cap-exchange
             connected
             quiescing       (settable)
             disconnecting   (settable)

Pg 37
     Remove ...TConnType
     Remove ...TConnAutoRetry      

    ..FlowCntlMode reorder enumeration
       undetermined,
       pacing,
       other,
       
     XBusy can be inferred from ..VersionString object  

Pg 38
     Remove SendWndwSize 
     Remove RecvWndwSize
      
Pg 39
    ..PartnerVersionString
    
       Text to describe how a pre-v1 peer would be known

Pg 38+ How do we get to the partner agent.

Pg 40  Partner*Escl now boolean (no other or unknown)

Pg 42  Disc Time is snapshot of ( not delta)

       Add ..DiscReason enum val
          other
          close idle
          close busy
          capex failed
          oper command
          on-demand tx goes to 0 connections

****** SESSION 3

Pg 22

---

From: [email-masked] (Ravi C. Periasamy)
Date: Mon, 10 Apr 1995 15:55:55 -0400

>     Howdy mibbers,
...<<<delete>>>...
>       5. Reception on 10th floor.
...<<<delete>>>...

You would think that Ravi (strange as it is) is unique. But we have about
3 "Ravi"s. So please ask for "Ravi Periasamy"!

Thanks,
Ravi Periasamy.

--------------------------
Ravi Periasamy,
[email-masked]
Ph: (vox) 919 878-6982
    (Fax) 919 878-6940
--------------------------